Ensuring accurate domain name contact information

ABSTRACT

Systems and methods of the present invention provide for one or more server computers communicatively coupled to a network and configured to: identify a first contact data and a second contact data associated with at least one domain name stored in a database communicatively coupled to the network; a user interface may be displayed, allowing a user to select the first contact data or a second contact data, and the server may then: receive a selection of the first contact data to be associated with the at least one domain name; disassociate the second contact data from the at least one domain name; and update a plurality of domain names, comprising the first domain name, to be associated with the first contact data.

FIELD OF THE INVENTION

The present inventions generally relate to the field of domain names andspecifically to the field of ensuring accurate contact informationassociated with a domain name.

SUMMARY OF THE INVENTION

The present inventions provide methods and systems comprising one ormore server computers communicatively coupled to a network andconfigured to: Identify a first contact data and a second contact dataassociated with at least one domain name stored in a databasecommunicatively coupled to the network. A user interface may bedisplayed, allowing a user to select the first contact data or a secondcontact data. The server may: receive a selection of the first contactdata to be associated with the at least one domain name; disassociatethe second contact data from the at least one domain name; and update aplurality of selected domain names, comprising the first domain name, tobe associated with the first contact data.

The present inventions may also provide methods and systems comprisingthe one or more server computers configured to: generate a code toverify a correspondence address associated with a geographical contactlocation for a domain name registrant; store the code in data storage230 in association with a domain name, possibly registered by theregistrant; retrieve a correspondence address within a domain namerecord for the domain name; generate a correspondence to be sent to thecorrespondence address including the code and a URL for accessing a userinterface for entering the code; determine whether the code has beenentered into the user interface; and if so, update the domain namerecord to include a status reflecting a verification of thecorrespondence address and a date of the verification.

The above features and advantages of the present invention will bebetter understood from the following detailed description taken inconjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a flow diagram illustrating a possible embodiment of a methodfor ensuring accurate domain name contact information.

FIG. 2 illustrates a possible system for ensuring accurate domain namecontact information.

FIG. 3 illustrates a more detailed possible system for ensuring accuratedomain name contact information.

FIG. 4 is a flow diagram illustrating a possible embodiment of a methodfor ensuring accurate domain name contact information.

FIG. 5 is a flow diagram illustrating a possible embodiment of a methodfor ensuring accurate domain name contact information.

FIG. 6 is a illustrates a user interface in a possible embodiment of amethod for ensuring accurate domain name contact information.

FIG. 7 is a illustrates a user interface in a possible embodiment of amethod for ensuring accurate domain name contact information.

FIG. 8 is a illustrates a user interface in a possible embodiment of amethod for ensuring accurate domain name contact information.

FIG. 9 is a illustrates a user interface in a possible embodiment of amethod for ensuring accurate domain name contact information.

FIG. 10 is a illustrates a user interface in a possible embodiment of amethod for ensuring accurate domain name contact information.

FIG. 11 is a illustrates a user interface in a possible embodiment of amethod for ensuring accurate domain name contact information.

FIG. 12 is a illustrates a user interface in a possible embodiment of amethod for ensuring accurate domain name contact information.

FIG. 13 is a flow diagram illustrating a possible embodiment of a methodfor ensuring accurate domain name contact information.

FIG. 14 is a flow diagram illustrating a possible embodiment of a methodfor ensuring accurate domain name contact information.

DETAILED DESCRIPTION

The present inventions will now be discussed in detail with regard tothe attached drawing figures that were briefly described above. In thefollowing description, numerous specific details are set forthillustrating the Applicant's best mode for practicing the invention andenabling one of ordinary skill in the art to make and use the invention.It will be obvious, however, to one skilled in the art that the presentinvention may be practiced without many of these specific details. Inother instances, well-known machines, structures, and method steps havenot been described in particular detail in order to avoid unnecessarilyobscuring the present invention. Unless otherwise indicated, like partsand method steps are referred to with like reference numerals.

A network is a collection of links and nodes (e.g., multiple computersand/or other devices connected together) arranged so that informationmay be passed from one part of the network to another over multiplelinks and through various nodes. Examples of networks include theInternet, the public switched telephone network, the global Telexnetwork, computer networks (e.g., an intranet, an extranet, a local-areanetwork, or a wide-area network), wired networks, and wireless networks.

The Internet is a worldwide network of computers and computer networksarranged to allow the easy and robust exchange of information betweencomputer users. Hundreds of millions of people around the world haveaccess to computers connected to the Internet via Internet ServiceProviders (ISPs). Content providers place multimedia information (e.g.,text, graphics, audio, video, animation, and other forms of data) atspecific locations on the Internet referred to as websites. Thecombination of all the websites and their corresponding web pages on theInternet is generally known as the World Wide Web (WWW) or simply theWeb.

Prevalent on the Web are multimedia websites, some of which may offerand sell goods and services to individuals and organizations. Websitesmay consist of a single webpage, but typically consist of multipleinterconnected and related web pages. Websites, unless extremely largeand complex or have unusual traffic demands, typically reside on asingle server and are prepared and maintained by a single individual orentity. Website browsers are able to locate specific websites becauseeach website, resource, and computer on the Internet has a uniqueInternet Protocol (IP) address.

IP addresses, however, even in human readable notation, are difficultfor people to remember and use. A Uniform Resource Locator (URL) is mucheasier to remember and may be used to point to any computer, directory,or file on the Internet. A browser is able to access a website on theInternet through the use of a URL. The URL may include a HypertextTransfer Protocol (HTTP) request combined with the website's Internetaddress, also known as the website's domain name.

Domain names are much easier to remember and use than theircorresponding IP addresses. The Internet Corporation for Assigned Namesand Numbers (ICANN) approves some Generic Top-Level Domains (gTLD) anddelegates the responsibility to a particular organization (a “registry”)for maintaining an authoritative source for the registered domain nameswithin a TLD and their corresponding IP addresses.

Registered domain names may be associated with contact information foreach registrant that registers a domain name. Often, when a registrantregisters a domain name, the registrar's user interface will collectcontact data about the registrant (possibly for WHOIS purposes,discussed below), and store the registrant's contact data in aone-to-one relationship with the domain name's registration data in theregistrar's database.

This one-to-one relationship between the registration data and thecontact data may be effective while the number of contacts and domainnames is small, but as each new redundant contact data is entered, thereis a greater likelihood of error (e.g., typographical errors,inconsistent spellings or capitalization), which may cause ambiguityabout whether the newly entered contact data is the same as a previouslyentered contact data, or whether the newly entered contact data isintended to be a new contact data associated with the registrant.

As noted above, WHOIS records may also be used to identifying and storeregistrant contact information. WHOIS records are generated andavailable via a transaction-oriented query/response protocol used toprovide domain name registration information services to Internet users.

Example domain name registration information may be seen in thefollowing simplified WHOIS record:

-   Registrant:

Dns Admin

Example Company Inc.

Please contact contact-admin@example.com

123 Example Parkway

Mountain View Calif. 94043

US

dns-admin@example.com +1.6502530000 Fax: +1.6506188571

Domain Name: example.com

Registrar Name: GoDaddy.com

Registrar Whois: whois.godaddy.com

Registrar Homepage: http://www.godaddy.com

-   Administrative Contact:

DNS Admin

Example Inc.

123 Example Parkway

Mountain View Calif. 94043

US

dns-admin@example.com +1.6501234567 Fax: +1.6501234567

-   Technical Contact, Zone Contact:

DNS Admin

Example Inc.

321 Example Street

Mountain View Calif. 94043

US

dns-admin@example.com +1.6507654321 Fax: +1.6507654321

-   Created on: Sep. 9, 2012.-   Expires on: Sep. 13, 2032.-   Record last updated on: Jan. 29, 2013.-   Domain servers in listed order:-   ns2.example.com-   ns4.example.com-   ns1.example.com-   ns3.example.com

In addition to the registrant's WHOIS data, the WHOIS record may alsoinclude additional contact data relevant to the domain nameregistration, such as administrative, technical, and billing informationfor the domain name.

The transparency into domain name ownership provided by WHOIS records,as well as the high value associated with some domain names, have causedsome unscrupulous individuals to hijack the registration and control ofdomain names. Domain name hijacking or domain name theft can involvechanging the registration of a domain name without the permission of itsoriginal registrant.

As non-limiting examples, a domain name hijacker may acquire personalinformation about the actual domain owner, possibly from WHOISinformation, and impersonate them in order to persuade the domainregistrar to modify the registration information and/or transfer thedomain name to another registrar (the hijacker), who would then gainfull control of the domain name.

To combat domain hijacking, domain name privacy services, such asGoDaddy's DOMAINS BY PROXY may be used to register domain namesanonymously, so that the contact data is the registrar's, rather thanthe registrant's. While such services provide anonymity for their users,they may endanger the registrant's ownership or control of the domainname if the associated domain name registry requires verification of aphysical addresses in a particular geographic location.

As a non-limiting example, the .nyc registry requires all domain nameregistrants to have a physical location in New York City or thesurrounding boroughs. The ambiguity caused by listing the registrar'sphysical address in a different physical location may cause theregistrant to forfeit its control of the domain name.

Thus, applicant has identified multiple weaknesses in presently existingmethods and systems for registering domain names. One weakness mayinclude the risk of losing a geographic-based domain name if a privacyservice creates ambiguity in the registrant's physical address. Anotherweakness in presently existing methods and systems includes theone-to-one relationship between a registrant's registration data andcontact data, which may create even more general ambiguity—existingmethods and systems do not allow a registrant to identify each contactdata as a single unique contact data that may be propagated consistentlythroughout all related domain registration and/or contact data.

Applicant has therefore identified methods that may improve onpresently-existing systems and methods. Optimal systems and methods mayinclude a system that verifies a single unique contact data for eachuser contact propagated throughout the existing registration and/orcontact data, and displays verification of the contact information,including physical address and date, within updated documents associatedwith the domain name (e.g., WHOIS, DNS, zone records, registrar webpages, etc).

Such verification may be accomplished by providing a registrant means toaccess all contact data and registrant data on record for the registrantand select each unique and independent contact data from a plurality ofcontact data. The registrant may also select one or more domain namesfrom the registration data to associate with one or more of thecontacts.

Software running on one or more servers may receive the selections ofeach contact user, generate a single unique record for each contact data(if not already existing), and delete all redundancies and errorsthroughout the stored contact data. This single unique record for eachstored contact may then be updated throughout all stored domain nameregistration data, possibly including associations with the domain namesselected by the user.

As a non-limiting example, software may be displayed to the user,including a list of all stored contacts for the user and another list ofall stored domain names registered to the user. Both lists may includecheckboxes to select the respective contact or domain name. The user maythen select the desired contacts and each contact to be associated withthe selected domain names.

Several different methods may be used to provide and manage the presentsystems. FIG. 1 represents a flow diagram for one possible embodiment ofthe previously described improvements on presently existing systems. Inthis example embodiment, one or more server computers may becommunicatively coupled to a network and operated by a hosting providerhosting a plurality of business websites. These server(s) may beconfigured to: Identify a first contact data and a second contact dataassociated with at least one domain name stored in a databasecommunicatively coupled to the network (Step 100); a user interface maybe displayed, allowing a user to select the first contact data or asecond contact data (Step 110). The server may then: receive a selectionof the first contact data to be associated with the at least one domainname (Step 120); disassociate the second contact data from the at leastone domain name (Step 130); and update a plurality of domain names,comprising the first domain name, to be associated with the firstcontact data (Step 140).

In other embodiments such as that shown in FIG. 14, the one or moreserver computers may be configured to: generate a code to verify acorrespondence address associated with a geographical contact locationfor a domain name registrant (Step 1400); store the code in data storagein association with a domain name, possibly registered by the registrant(Step 1410); retrieve a correspondence address within a domain namerecord for the domain name (Step 1420); generate a correspondence to besent to the correspondence address including the code and a URL foraccessing a user interface for entering the code (Step 1430); determinewhether the code has been entered into the user interface (Step 1440);and if so, update the domain name record to include a status reflectinga verification of the correspondence address and a date of theverification (Step 1450).

Several different environments may be used to accomplish the methodsteps of embodiments disclosed herein. FIG. 2 demonstrates a streamlinedexample and FIG. 3 demonstrates a more detailed example of anenvironment including a system and/or structure that may be used toaccomplish the methods and embodiments disclosed and described herein.Such methods may be performed by any central processing unit (CPU) inany computing system, such as a microprocessor running on at least oneserver 210 and/or client 220, and executing instructions stored (perhapsas scripts and/or software, possibly as software modules/components) incomputer-readable media accessible to the CPU, such as a hard disk driveon a server 210 and/or client 220.

The example embodiments shown and described herein exist within theframework of a network 200 and should not limit possible networkconfiguration or connectivity. Such a network 200 may comprise, asnon-limiting examples, any combination of the Internet, the publicswitched telephone network, the global Telex network, computer networks(e.g., an intranet, an extranet, a local-area network, or a wide-areanetwork), a wired network, a wireless network, a telephone network, acorporate network backbone or any other combination of known or laterdeveloped networks.

At least one server 210 and at least one client 220 may becommunicatively coupled to the network 200 via any method of networkconnection known in the art or developed in the future including, butnot limited to wired, wireless, modem, dial-up, satellite, cable modem,Digital Subscriber Line (DSL), Asymmetric Digital Subscribers Line(ASDL), Virtual Private Network (VPN), Integrated Services DigitalNetwork (ISDN), X.25, Ethernet, token ring, Fiber Distributed DataInterface (FDDI), IP over Asynchronous Transfer Mode (ATM), InfraredData Association (IrDA), wireless, WAN technologies (T1, Frame Relay),Point-to-Point Protocol over Ethernet (PPPoE), and/or any combinationthereof.

The example embodiments herein place no limitations on whom or what maycomprise users. Thus, as non-limiting examples, users may comprise anyindividual, entity, business, corporation, partnership, organization,governmental entity, and/or educational institution that may haveoccasion to organize/import contacts and/or send marketing campaigns.

Server(s) 210 may comprise any computer or program that providesservices to other computers, programs, or users either in the samecomputer or over a computer network 200. As non-limiting examples, theserver 210 may comprise application, communication, mail, database,proxy, fax, file, media, web, peer-to-peer, standalone, software, orhardware servers (i.e., server computers) and may use any server formatknown in the art or developed in the future (possibly a shared hostingserver, a virtual dedicated hosting server, a dedicated hosting server,a cloud hosting solution, a grid hosting solution, or any combinationthereof) and may be used, for example to provide access to the dataneeded for the software combination requested by a client 220.

The server 210 may exist within a server cluster, as illustrated. Theseclusters may include a group of tightly coupled computers that worktogether so that in many respects they can be viewed as though they area single computer. The components may be connected to each other throughfast local area networks which may improve performance and/oravailability over that provided by a single computer.

The client 220 may be any computer or program that provides services toother computers, programs, or users either in the same computer or overa computer network 200. As non-limiting examples, the client 220 may bean application, communication, mail, database, proxy, fax, file, media,web, peer-to-peer, or standalone computer, cell phone, personal digitalassistant (PDA), etc. which may contain an operating system, a full filesystem, a plurality of other necessary utilities or applications or anycombination thereof on the client 220. Non limiting example programmingenvironments for client applications may include JavaScript/AJAX (clientside automation), ASP, JSP, Ruby on Rails, Python's Django, PHP, HTMLpages or rich media like Flash, Flex or Silverlight.

The client(s) 220 that may be used to connect to the network 200 toaccomplish the illustrated embodiments may include, but are not limitedto, a desktop computer, a laptop computer, a hand held computer, aterminal, a television, a television set top box, a cellular phone, awireless phone, a wireless hand held device, an Internet access device,a rich client, thin client, or any other client functional with aclient/server computing architecture. Client software may be used forauthenticated remote access to a hosting computer or server. These maybe, but are not limited to being accessed by a remote desktop programand/or a web browser, as are known in the art.

The user interface displayed on the client(s) 220 or the server(s) 210may be any graphical, textual, scanned and/or auditory information acomputer program presents to the user, and the control sequences such askeystrokes, movements of the computer mouse, selections with a touchscreen, scanned information etc. used to control the program. Examplesof such interfaces include any known or later developed combination ofGraphical User Interfaces (GUI) or Web-based user interfaces as seen inthe accompanying drawings, Touch interfaces, Conversational InterfaceAgents, Live User Interfaces (LUI), Command line interfaces, Non-commanduser interfaces, Object-oriented User Interfaces (OOUI) or Voice userinterfaces. The commands received within the software combination, orany other information, may be accepted using any field, widget and/orcontrol used in such interfaces, including but not limited to atext-box, text field, button, hyper-link, list, drop-down list,check-box, radio button, data grid, icon, graphical image, embeddedlink, etc.

The server 210 may be communicatively coupled to data storage 230including any information requested or required by the system and/ordescribed herein. The data storage 230 may be any computer components,devices, and/or recording media that may retain digital data used forcomputing for some interval of time. The storage may be capable ofretaining stored content for any data required, on a single machine orin a cluster of computers over the network 200, in separate memory areasof the same machine such as different hard drives, or in separatepartitions within the same hard drive, such as a database partition.

Non-limiting examples of the data storage 230 may include, but are notlimited to, a Network Area Storage, (“NAS”), which may be aself-contained file level computer data storage connected to andsupplying a computer network with file-based data storage services. Thestorage subsystem may also be a Storage Area Network (“SAN”—anarchitecture to attach remote computer storage devices to servers insuch a way that the devices appear as locally attached), an NAS-SANhybrid, any other means of central/shared storage now known or laterdeveloped or any combination thereof.

Structurally, the data storage 230 may comprise any collection of data.As non-limiting examples, the data storage 230 may comprise a localdatabase, online database, desktop database, server-side database,relational database, hierarchical database, network database, objectdatabase, object-relational database, associative database,concept-oriented database, entity-attribute-value database,multi-dimensional database, semi-structured database, star schemadatabase, XML database, file, collection of files, spreadsheet, and/orother means of data storage such as a magnetic media, hard drive, otherdisk drive, volatile memory (e.g., RAM), non-volatile memory (e.g., ROMor flash), and/or any combination thereof.

The server(s) 210 or software modules within the server(s) 210 may usequery languages such as MSSQL or MySQL to retrieve the content from thedata storage 230. Server-side scripting languages such as ASP, PHP,CGI/Perl, proprietary scripting software/modules/components etc. may beused to process the retrieved data. The retrieved data may be analyzedin order to determine the actions to be taken by the scripting language,including executing any method steps disclosed herein.

The software modules/components of the software combination used in thecontext of the current invention may be stored in the memory of—and runon—at least one server 210. As non-limiting examples of such software,the paragraphs below describe in detail the software modules/componentsthat make up the software combination. These software modules/componentsmay comprise software and/or scripts containing instructions that, whenexecuted by a microprocessor on a server 210 or client 220, cause themicroprocessor to accomplish the purpose of the module/component asdescribed in detail herein. The software combination may also shareinformation, including data from data sources and/or variables used invarious algorithms executed on the servers 210 and/or clients 220 withinthe system, between each module/component of the software combination asneeded.

A data center 240 may provide hosting services for the softwarecombination, or any related hosted website including, but not limited tohosting one or more computers or servers in a data center 240 as well asproviding the general infrastructure necessary to offer hosting servicesto Internet users including hardware, software, Internet web sites,hosting servers, and electronic communication means necessary to connectmultiple computers and/or servers to the Internet or any other network200.

FIG. 3 shows a more detailed example embodiment of an environment foraccomplishing the systems and method steps disclosed herein. Asnon-limiting examples, all disclosed software modules may run on one ormore server(s) 210 and may include one or more user interfaces generatedby the server(s) 210 and transmitted to and displayed on the client(s)220. The user interface(s) may be configured to receive input from theuser and transmit this input to the server(s) 210 for the administrationand execution of the software, using data in data storage 230 associatedwith the software modules.

As seen in FIG. 3, server(s) 210 may host and/or run one or more contactadministration software modules 310, which may be configured to executeany or all of the method steps disclosed herein.

Server(s) 210 may be hosted by any entity, possibly a hosting provider,a domain name registrar, a website development company, any othersoftware service provider or any combination thereof. To manage users ofsuch a system, including individuals or organizations, server(s) 210 mayhost and run a user administration program such as GoDaddy's My Accountcontrol panel for managing hosting and domain names, as a non-limitingexample.

In such an administration control panel program, or admin, each user maybe assigned a user id. This user id may identify transactions performedby each user. These transactions may be stored as data records in datastorage 230, each data record including the user id to associate theuser with the transaction in the database. As non-limiting examples,transactions in the context of the disclosed inventions may includereceiving and storing a user contact 300 and/or receiving a domain nameregistration data 305.

As seen in FIG. 3, server(s) 210 may host and/or store data for one ormore contacts, stored as user contact data 300 and associated in datastorage 230 with a user id. If the individual or organization associatedwith the user id is a domain name registrant, then data from theregistration of the domain name may be stored as domain nameregistration data 305 in data storage 230. The domain registration data305 may be associated with the user id and mapped to the user contactdata 300.

The user contact data 300 may exist independent of the domainregistration data 305. Domain registration data 305 may be associatedwith a user id and further mapped to a user contact data 300, but animportant goal of the current invention is to include a unique instanceof each user contact data 300 in data storage, thereby guaranteeingconsistency between displayed contacts by propagating the contact data300 throughout the system from a single unique contact data 300.

Thus, a single unique instance of each user contact data may exist indata storage 230, but may be associated with multiple domain nameinstances. Likewise, a single domain name instance may be associatedwith multiple unique contact instances.

The user data, user contact data 300 and domain name registration data305 may be stored as user data records, contact data records and domainname data records respectively, possibly associated via joins withindata storage 230. As a non-limiting example, data storage 230 maycomprise a user data table, a user contacts data table and a domainregistration data table.

The user data table may comprise the user id, possibly included in theuser contact data records 300 and/or domain registration data records305 to associate these records with the individual and/or organization.In some embodiments, the user data table may include data such as ausername, password, API and/or other URL to access contacts data withina social media account for an individual or organization, or to access aHuman Resources (HR) contacts database for an organization, in order tomonitor and verify accurate user contact data 300, described in moredetail herein.

The user contacts data table may comprise one or more individual andunique data records for each contact associated with a particular userid, possibly including information such as an organization name, aphysical address (number, street, town, city, country), telephone number(cell, landline), a fax, a company URL (i.e., an address for a companyhome page), or an email address.

Each user may be associated with multiple contact data, as seen in theexample WHOIS record above. As non-limiting examples, if the user is anorganization, the user contact data 300 may include an administrativecontact (possibly including a DNS admin), a technical contact, a domainname zone contact, a billing contact, etc. Each of these contacts may beunique and independent of each other and of any domain registration data305 stored in data storage 230.

In some embodiments, logic within one or more contact administrationsoftware modules 310 may dynamically display a different contactinformation based on current daylight hours. As a non-limiting example,the user contact data 300 may comprise a contact data 300 for atechnical contact in the United States, a technical contact in Japanand/or a Technical contact in Europe. The software logic may dynamicallyupdate any displayed contact information so that during daytime hours inthe US, the US technical contact is displayed, during daytime hours inJapan, the Japan contact is displayed and so forth.

The domain name registration data table may comprise data stored inrelation to each domain name registered by the user, each data record inthe domain registration data table including the user id associated withthe data record. As non-limiting examples, domain registration data 305may comprise a domain name, a registrar, a registrar URL (i.e., aregistrar homepage or domain name registration tool), additional WHOIS,DNS or zone record information, etc.

In some embodiments, domain registration data 305 may also comprise auser contact data 300 collected during the domain name registration.User contact data 300 stored with the domain registration data 305 mayalso exist from pre-existing domain registration data prior tointegration of the disclosed system or as domain registration data 305imported into the database, possibly during a domain name transfer fromanother register. This combined domain registration data 305 and usercontact data 300 may be consolidated into independent contact data 300using the methods disclosed herein.

In some embodiments, user contact data 300 and/or domain registrationdata 305 may be added to the data storage via a user manually enteringthe user contact data 300 and/or domain registration data 305 into auser interface.

In these or other embodiments, a user may want to compare all availableuser contact data 300 with all available domain registration data 305 toinitially correlate and/or maintain the associations between the two. Inthese embodiments, the user may be presented with a list of user contactdata 300 and another list of domain registration data 305. The user mayselect which domain registration data 300 to associate with which usercontact data 305. As noted above, in some embodiments, each user contactdata 300 in the list may include a checkbox for the user to select thecontact data 300. Each domain registration data 305 may also have acheckbox, so that the user may select a plurality of domain registrationdata 305 to be applied to a plurality of user contact data 300. The userinterface may also comprise means for the user to update any details ofthe contact information (e.g., text boxes allowing user to edit and/orinsert contact information).

More granular embodiments may exist, where the user may select a singleuser contact data 300, possibly via a radio button, drop down, touchscreen selection, etc., and may select, possibly via checkboxes, aplurality of domain registration data 305 to be associated with thatuser contact data 300. Conversely, other embodiments may exist where theuser selects a single domain registration data 305 and associatesmultiple contacts with that domain name. These examples should in no waylimit the possible combinations of displayed domain names that areassociated with contacts and vice versa.

In embodiments where only one user contact data 300 is associated withthe user id, no interface for associating the user contact data 300 withthe domain registration data 305 is necessary, and all domainregistration data 305 may be automatically associated with the singleuser contact data 300.

However, additional embodiments may include interfaces and theunderlying software logic to capture all possible combinations ofassociating contact data 300 with domain name registration data 305. Inone example embodiment, a user may be presented with an option to applyall user contact data 300 with all domain registration data 305. Forexample, if an organization knew it wanted to apply all of its knowncontacts (e.g., administration, technical, domains, billing contacts) toall of its registered domains, it may select this option on a userinterface, and the selected options may be propagated throughout thecontact data 300 and/or domain name registration data 305 stored in datastorage.

Another example embodiment may include a more efficient means for anorganization or a web professional for the organization to select thecontact data 300 and/or domain name registration data 305 by groups, sothat individual selections are not needed. As non-limiting examples, thecontact data 300 may be displayed on the user interface in groups ofcommon contact data 300 to be selected, and possibly consolidated. Inother words, in order to consolidate several stored contacts into asingle independent contact, the user may be presented with all contactdata 300 including common data such as organization name, physicaladdress data, email address, etc. The user may then select one or moreof these contacts from the group to be propagated throughout the system.

Likewise, the domain name registration data 305 may also be displayed bygroups of common domain name registration data 305 on the user interfaceto be selected. Non-limiting examples of groupings of domain nameregistration data 305 may include domain names with the same secondlevel domain but a different top level domain (e.g., godaddy.com,godaddy.net, godaddy.org, etc.), domain names sharing a common IPaddress, domain names sharing a common MX record, etc.

The current invention may provide for consolidating a plurality ofdomain registration data 305 into unique and independent contact data300 to be propagated throughout the system. However, user contact data300 may be added to data storage 230 via external sources including, asnon-limiting examples, importing contact data 300 collected duringdomain name registrations (e.g., user-entered WHOIS data) and/orsynchronizing/importing user contact data 305 from an API, data feed orother network connection with a social media account or an HR departmentdatabase. More specifically, contact administration software 310 may usethe username, password, URL or other disclosed data above to access usercontact data 300 stored in a social media account and/or listed in an HRdatabase.

Contact administration software 310 may determine if at least one usercontact data 305 associated with the user id exists in the disclosedsystem. If not, software may add the user contact data from the socialmedia and/or HR data feed to data storage 230, and may associate it withthe user id. If user contact data 305 already exists for the identifieduser, contact administration software 310 may determine if the socialmedia and/or HR contact matches any stored user contacts 300.

If the social media or HR contact is an exact match, the system mayproceed as normal. If contact administration software 310 determinesthat there are only minor differences between the social media and/or HRcontact and a stored contact, the system may present the similarcontacts to the user in order to determine the desired correct contactdata 300 as described in association with alerts below.

In addition to the previously described contact data from externalsources, domain registration data 305 may be imported from one or moreadditional external sources that have integrated the contact data 300into the domain name registration data 305. Non limiting examples ofsuch domain registration data 305 may include domain registrationrecords received prior to implementation of the current invention anddomain registration data 305 imported from other sources, such as duringa domain name migration and/or transfer.

FIG. 4 is a flowchart outlining a possible method for consolidating usercontact data 300 integrated into the domain registration data 305 andgenerating user contact data 300 independent of the domain registrationdata 305. In these embodiments, contact administration software 310 mayidentify user contact data 300 integrated into the domain registrationdata 305 (Step 400). Contact administration software may then extractthe user contact data 300 from the domain registration data 305 (Step410), and may generate a new independent user contact data 300 from dataextracted from each domain registration data 305 (Step 420).

FIG. 5 is a flowchart outlining a possible method for identifying twopossible redundant contacts and confirming, with the user, which usercontact data 300 should be the unique and independent user contact data300 stored in data storage 230.

In all embodiments, including both user-generated, external resourcesgenerated, and extracted user contact data 300, each user contact data300 may be compared with each other user contact data 300 in order toidentify redundancies and/or errors (e.g., typographical or othererrors) with the user contact data 300, thereby ensuring that eachstored user contact data 300 comprises only correct data (Step 500) tobe propagated throughout the system.

Contact administration software 310 may analyze and compare each usercontact data 300 and compare it against each other user contact data300, searching for identical or common text strings (Step 505). Commontext strings may comprise, but are not limited to, any text string withsimilar but inconsistent information.

As a non-limiting example, contact administration software 310 mayanalyze and compare two user contact data records and determine that thecompany, street address, state and zip code data is identical for both.However, one data record may contain city data for “Mountainview,” whilethe other contains city data of “mountain view.”

Software may tokenize both of the suspected user contact data recordsand determine that both contain the tokens “mountain” and “view” withminor differences between spacing and capitalization (Step 510). Contactadministration software 310 may further compare the domain registrationdata 305 associated with each of the suspect records and determine thatboth contacts are associated with the same domain registration data 305(Step 515).

Having established a need for clarification from the user to confirmthat these are the same user contact data 300 and to request the user toselect a single unique and independent user contact data 300 to bepropagated throughout the system, contact administration software 310may generate and transmit an alert requesting this clarification andinput from the user (Step 520). As discussed below, such alerts may alsobe triggered by changes and/or differences between monitored usercontact data 315 and stored user contact data 300.

The alert may be displayed via an email to the user associated with theuser id, possibly using any email address stored in user data in datastorage 230, or may be displayed to the user via the admin software orany other user interface available to the user.

The alert may comprise information explaining the need for action fromthe user. In this example, the information may comprise the user contactdata 300 that is being compared, the similarities and/or the differencesin the text strings of the respective user contact data 300 and/or thedomain registration data 305 associated with the user contact data 300.In the embodiments below, the need for action from the user may betriggered by any change and/or difference between the user contact data300 or the monitored user contact data 315.

In addition to the information explaining the need for action from theuser, the alert may comprise a user interface comprising any userinterface elements. As a non-limiting example, the user interface maycomprise a listing of the user contact data 300 and the associateddomain registration data 305. Each user contact data 300 may include alink, button, checkbox, radio button, dropdown, etc., allowing the userto select that user contact data 300 as the single unique andindependent user contact data 300 selected by the user to be stored indata storage 230. It should be noted, however, that additional optionsmay exist allowing the user to maintain multiple similar user contactdata 300.

The user's selection(s) may then be transmitted from the client on whichthe user interface is displayed, to server(s) 210. Server(s) 210 mayreceive the user selection, and the selection, possibly including theassociation of the user contact data 300 with one or more or more domainname data 305 may be propagated throughout data storage 230 and/orthroughout the system.

Thus, the user interface may comprise a one click solution, receiving aselection from the user and updating all selected instances of the usercontact data 300 and/or any associated domain registration data 305. Inother words, all instances of the selected contact data 300 may beassociated with all instances of the selected domain registration data305 throughout data storage 230, and vice versa. It should be notedagain that these associations are not within individual data recordsthemselves Rather, the data records for contacts and the data recordsfor domain names exist independent of one another, but may be joined inthe database.

In any of these embodiments presenting the contacts to the user via auser interface, any user contact data 300 that is not selected may bedeleted, disregarded and/or disassociated generally, and/or may bedisassociated with domain registration data 305 in data storage 230.This disassociation or deletion may also be propagated throughout datastorage 230 or throughout the system.

In some embodiments, the user interface displayed on the client mayinclude an option to defer this propagation for a length of timeselected by the user. If the user is a large corporation, changes incontact information may signal changes indicating a location changeand/or a fundamental strategy for the company. Contact administrationsoftware 310 may be configured to delay the propagation of the usercontact data 300 and/or domain registration data 305 selected for adesignated period of time so that the contact/domain registration changewill not become generally known until desired.

In some embodiments, contact administration software 310 may determine auser contact data 300 with the most common usage and the user interfacemay present this most common usage as part of the alert, asking the userif this contact should be propagated throughout the database. The usermay be presented a button or link allowing them to confirm, and if so,the contact may be propagated throughout the database and system,disassociating any non-selected contact as previously described.

FIGS. 6-12 demonstrate a plurality of possible user interfaces in thedisclosed embodiments. In the example interface shown in FIG. 6, a usermay select the desired domains. In the example interface shown in FIG.7, a user may select the types of contact types to be stored as uniqueand independent data in data storage 230. FIG. 8 demonstrates an exampleinterface listing all contacts associated with the user in data storage,possibly via a user ID. This interface provides means for a user toselect contacts and update them in data storage 230. FIG. 9 shows anexample user interface for selecting contacts as above, with anadditional feature for displaying the number of domains associated witheach listed contact. The user may update this contact data andassociated domain name data in data storage 230. FIG. 10 demonstrates anexample user interface used to edit current contact information. Asnon-limiting examples, a user may add/edit a name, physical address,city, state, phone number and/or email address for the contact andupdate accordingly.

FIG. 11 is an example interface demonstrating contacts associated withmultiple domains. This example interface provides means for a user toview, add, replace and/or otherwise update new contacts associated withone or more domain names. FIG. 12 is an example interface demonstratingsimilar features, but further displaying and/or allowing the user toupdate the type of contact (e.g., registrant, admin, billing, technical)associated with each contact for the one or more domain names.

As seen in the non-limiting example embodiment in FIG. 13, the systemmay monitor several resources to ensure that the user contact data 300stored in data storage 230 is synchronized with all monitored usercontact data 315 external to the system (Step 1300), and may generate arequest for user input if the monitored user contact data 315 changes(Step 1310). The system may generate notifications that the stored usercontact data 300 does not match the external monitored user contact data315 and ask the user to confirm, using the previously disclosed alertprocess, whether the stored contact data 300 or the external monitoreduser contact data 315 is the correct contact to be propagated throughoutthe system. As above, the alert may be displayed within an email or viaany user interface, as non-limiting examples.

External monitored user contact data sources 315 may include socialmedia contacts, HR contact data synchronized with the disclosed system,updates available through the US postal service (USPS) including variousmeans of determining if customers have changed address, etc.

In some embodiments, the geographical location of the user or the user'sorganization may be verified using online mapping software. Asnon-limiting examples, Google Maps or Mapquest may provide streetaddresses and names of places (e.g., the storefront existed as of Nov.9, 2014), possibly via an API similar to those described herein, so theaddress may be verified.

The social media information stored in association with user data indata storage 230, possibly associated with the user id, may be used toconnect to a social media API, data stream and/or other networkconnection. This API or data stream may provide access to a monitoreduser contact data 315 associated with the user, possibly a businessaddress for the social media account. As non-limiting examples, thesocial media API or data stream may access a monitored user contact data315 from Facebook, Yelp, Google Listings, Locu Listings, etc.

The system may be alerted when this monitored user contact data 315changes (Step 1310) or may otherwise regularly check to see if themonitored user contact data 315 for the social media matches the storeduser contact data 300 in the system for the user. If not, an alert maybe sent to the user to update the contact information, and the user mayupdate the stored user contact data 300 as disclosed herein.

In some embodiments, a partnership with an organization's HR departmentor an API or other network data stream may be used to determine thecontact information stored in a database for the HR department. This APIor data stream may provide access to a contact data associated with theuser, possibly including business contact data (e.g., technical, zone,billing, etc.) for the designated employees of the organization.

The system may be alerted when this monitored user contact data 315changes (Step 610) or may regularly check to see if the user contactdata 315 for the HR department matches the stored user contact data 300for the user. If not, an alert may be sent to the user to update theuser contact data 300, and the user may update the user contact data 300as disclosed herein.

In the social media and HR database embodiments, as well as all otherembodiments disclosed herein, the system may automatically update theuser contact data 300 to match the monitored user contact data 315without user interaction, so that the user contact data 300 is alwayssynchronized in real time.

The system may synchronize the stored user contact data 300 withmonitored user contact data 315 from the USPS to identify discrepanciesin existing contacts or changes to the USPS contact data (Step 1310).This synchronizing may be accomplished via electronic means or by postaldelivery methods.

Although the disclosed non-limiting example embodiments are specific tothe USPS, no limitations should be made on the means through which auser's geographical location. As non-limiting examples, the verificationcould be made in person (e.g., courier, Uber driver, Taskrabbit, etc.).The user's geographical location could also be verified via anyavailable commercial delivery services specializing in physical mail orpackage delivery (e.g., FedEx, UPS, etc.).

In addition, these commercial delivery services, as well as the servicesthat use them, (e.g., Amazon, credit card companies) may further augmentthe functionality of the disclosed invention to provide a more granularverification of a user's geographical location, using any availableproprietary tracking software, to identify name and address combinationsfor particular users, and may verify these names and addresses using theactions correlated to these names and addresses (e.g., signing for apackage, calling in to verify a credit card number, voter registrations,etc.).

Electronic means for synchronizing postal information may comprise oneor more APIs accessible via the USPS website/software that monitors auser's current physical address and any changes to their monitored usercontact data 315. The administrator of the disclosed system may need topartner with the USPS to gain access to these resources.

Non-limiting examples of USPS APIs may include the USPS web tools APIand the USPS ecommerce API. Additional USPS online tools may trackchanges for financial purposes, but may be modified to include anymethod steps disclosed herein. Any of these resources may be configuredto alert the user and/or the disclosed system that: a user has changedtheir monitored user contact data 315; a user has requested that mail beforwarded to a different address than the monitored user contact data315; and/or that mail sent to the monitored user contact data 315 hasbeen returned, is undeliverable or has otherwise bounced.

Postal delivery methods may include sending a correspondence, possiblyincluding an email, postcard and/or letter, via a certain level of USPSservice, to a correspondence address stored in data storage 230, themonitored user contact data 315 and/or any other disclosed domain namerecord, and tracking its progress. If the correspondence isundeliverable, returned, forwarded or otherwise bounced, the user and/orsystem may be alerted that the stored user contact data 300, includingthe correspondence address, is no longer valid, and may generate analert to the user via email or user control panel to confirm the correctaddress, as previously disclosed.

In embodiments such as those seen in FIG. 14, confirmation of thecorrespondence address may be used to verify the contact's physicalgeographical contact location, and may update the domain name record(s)to reflect this verification.

In some embodiments, user contact data 300 may use a privacy service,such as GoDaddy's DOMAINS BY PROXY. This service may list a registrar'scontact information in domain name records, such as WHOIS records, DNSrecords, zone files and/or domain name related data records in datastorage 230, in order to protect a registrant's privacy.

To avoid concerns with maintaining nexus requirements of a registrywhile still protecting user information privacy, the current system mayverify the existence of a “physical store front” for the domain namecontacts by generating a verification of the registrant's geographicallocation, including the correspondence address. The USPS embodimentsdescribed herein may confirm that the stored user contact data 300listed is in fact a legitimate physical geographical location for theuser.

As seen in FIG. 14, the disclosed software running on server(s) 210 maybe configured to: generate a code to verify a correspondence addressassociated with a geographical contact location for a domain nameregistrant (Step 1400); store the code in data storage 230 inassociation with a domain name, possibly registered by the registrant(Step 1410); retrieve a correspondence address within a domain namerecord for the domain name (Step 1420); generate a correspondence to besent to the correspondence address, including the code and a URL foraccessing a user interface for entering the code (Step 1430); determinewhether the code has been entered into the user interface (Step 1440);and if so, update the domain name record to include a status reflectinga verification of the correspondence address and a date of theverification (Step 1450).

In some embodiments, the correspondence may comprise a code used toverify a user's physical geographical contact location. This code maycomprise a personal identification number (PIN) or a quick response (QR)code associated with a domain name registered to a registrant and/or maybe associated with the registrant via the user's account. This code maybe used to verify receipt of the correspondence by entering the codeinto the user interface displayed when the URL is entered into abrowser, in order to confirm that the stored user contact data iscorrect, having been delivered to the correspondence address listed inthe current domain name record(s). In some embodiments, the QR code maybe scanned to confirm receipt of the correspondence.

In some embodiments, if the correspondence is tracked and the systemdetermines, possibly via the disclosed APIs, that the correspondence wasforwarded, the system may track the address that the correspondence wasforwarded to, and may update the stored user contact data 300, includingthe correspondence address, and/or may confirm the address via sendingan alert to the user to confirm the address as previously described.

In some embodiments, the correspondence may be dispatched in response toany detected update, change and/or any other contact data discrepancybetween the monitored user contact data 315, the stored user contactdata 300, and/or any other disclosed domain name records. The system mayrequire that the user enter the code into the user interface found atthe URL in order to confirm the stored user contact data 300, includingthe correspondence address, on record for that user. Contactadministration software 310 may detect the discrepancy and automaticallysend the correspondence to the correspondence address. Until the code isentered into the user interface at the designated URL, contactadministration software 310 may freeze any activity, or otherwisesuspend the account associated with the suspect user contact data 300,including the correspondence address, in data storage 230.

In some embodiments, correspondence may be sent regularly to allcontacts to confirm they are still current. If no code is received viathe user interface at the designated URL, or if the correspondence isreturned, undeliverable, forwarded and/or bounced, an alert as describedabove, as well as correspondence including the code and URL, may be sentto the user via any means to have the user update their user contactdata 300.

The verification generated by the server(s) and displayed in the domainrecords may include a logo displayed in association with the domain nameor contact (e.g., when displayed in a domain name aftermarket listing),or may include a verification of a certain contact within adomain-related record, such as a WHOIS record, a DNS record or a zonefile, as non-limiting examples.

The updates to the domain-related record(s) may include a tag confirmingthe verified contact. This tag may comprise any additional text and maycomprise a status of the contact data to be verified and the date ofverification (e.g., “correspondence address verified Jan. 1, 2014”) Asanother non-limiting example, a .nyc domain record may be updated toinclude a tag that reads “address in nyc verified,” and include the datethat the contact data was verified.

This process of verifying the user's correspondence address may berepeated at regular intervals (e.g., every year) and if thecorrespondence address is not verified, the status, as well as the tagmay change to “pending verification.” If the pending verification tag isin place for too long, the domain name may be put on an unverifiedstatus, and the user, registrar and/or registry may work together to getthe domain name and/or contact data verified again for purposes ofregistry/registrar requirements such as a physical storefront for .nyc

The steps included in the embodiments illustrated and described inrelation to FIGS. 1-14 are not limited to the embodiment shown and maybe combined in several different orders and modified within multipleother embodiments. Although disclosed in specific combinations withinthese figures, the steps disclosed may be independent, arranged andcombined in any order and/or dependent on any other steps orcombinations of steps.

Other embodiments and uses of the above inventions will be apparent tothose having ordinary skill in the art upon consideration of thespecification and practice of the invention disclosed herein. Thespecification and examples given should be considered exemplary only,and it is contemplated that the appended claims will cover any othersuch embodiments or modifications as fall within the true scope of theinvention.

The Abstract accompanying this specification is provided to enable theUnited States Patent and Trademark Office and the public generally todetermine quickly from a cursory inspection the nature and gist of thetechnical disclosure and in no way intended for defining, determining,or limiting the present invention or any of its embodiments.

The invention claimed is:
 1. A method, comprising the steps of:Identifying, by a server computer communicatively coupled to a network,a first contact data and a second contact data associated with at leastone domain name stored in a database communicatively coupled to thenetwork; receiving, by the server computer, a selection of the firstcontact data to be associated with the at least one domain name;disassociating, by the server computer, the second contact data from theat least one domain name; and updating, by the server computer, aplurality of domain names, comprising the at least one domain name, tobe associated with the first contact data.
 2. The method of claim 1,wherein first contact data comprises a unique data record mapped to theat least one domain name.
 3. The method of claim 1, wherein the secondcontact data comprises: a new user contact data record generated by auser; or a data record generated during a domain name registration ortransfer and comprising a user contact data.
 4. The method of claim 1,further comprising the steps of: rendering, by the server computer, auser interface to be displayed on a client computer communicativelycoupled to the network, the user interface comprising: a list of aplurality of contact data comprising the first contact data and thesecond contact data; and a list of the plurality of domain names;receiving, by the server computer, a selection via the user interface,comprising: the first contact data; and the at least one domain name. 5.The method of claim 1, wherein the first contact data comprises a socialmedia contact data.
 6. The method of claim 1, further comprising thesteps of: identifying, by the server computer: a text string common tothe first contact data and the second contact data; and at least onedifference between the first contact data and the second contact data;generating, by the server computer, a user interface comprising the atleast one difference and configured to receive the selection of thefirst contact data.
 7. The method of claim 1, further comprising thesteps of: Identifying a user id associated with the first contact data;and associating the plurality of domain names with the user id.
 8. Asystem, comprising: a database communicatively coupled to a network andcomprising: a plurality of contact data comprising a first contact dataand a second contact data; a plurality of domain registration datacomprising a plurality of domain names; a server computercommunicatively coupled to a network and configured to: identify anassociation within the database between at least one of the plurality ofdomain names and the first contact data and the second contact data;receive a selection of the first contact data to be associated with theat least one of the plurality of domain names; disassociate the secondcontact from the at least one of the plurality of domain names; andupdate a plurality of domain names to be associated with the firstcontact data.
 9. A method, comprising the steps of: monitoring, by aserver computer communicatively coupled to a network, a monitoredcontact data associated with a stored contact data; identifying, by thesever computer, an update to the monitored contact data; receiving, bythe server computer, a selection of the monitored contact data to beassociated with at least one domain name stored in a databasecommunicatively coupled to the network; disassociating, by the servercomputer, the stored contact from the at least one domain name; andupdating, by the server computer, a plurality of domain names,comprising the at least one domain name, to be associated with themonitored contact data.
 10. The method of claim 9, wherein the monitoredcontact data comprises: a social media contact data associated with asocial media account; or a postal contact monitored by a postal service.11. The method of claim 10, wherein the postal contact comprises: anapplication programming interface comprising a user address; or apostcard or letter sent to the user address.
 12. The method of claim 11,wherein the postcard or letter comprises a personal identificationnumber to be entered into a user interface to verify the stored contact.13. The method of claim 12, wherein, responsive to the update, thepostcard or letter Is sent to the user address.
 14. The method of claim13 further comprising the steps of: sending the postcard or the letterto the user address at regular intervals; responsive to the personalidentification number being entered into the user interface, changing astatus for the stored address to a verified status; and responsive tothe personal identification number not being entered into the userinterface after a designated time period, changing the status for thestored address to a verification pending status.
 15. The method of claim14 further comprising the step of Inserting the verification status intoa domain name related record.